[ENG-3771] projects-cli-1: default project UX#677
Conversation
ac843d0 to
dbe9200
Compare
|
@mrmoxon thoughts on folding this into the setup flow? ie default = single project that shares name with workspace folder, overridable + switchable. a bit worried about abstraction creep, feels like we can have these coupled until users explicitly want to decouple |
Defo agree, am making the |
|
Addressed the setup-flow point: |
530dca9 to
38348e9
Compare
|
Rebased onto latest |
38348e9 to
db89b50
Compare
a70e00e to
1c9b467
Compare
62608b7 to
6d0e97c
Compare
1c9b467 to
3be9bd9
Compare
6d0e97c to
65d3769
Compare
3be9bd9 to
4560fd8
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 4560fd8. Configure here.
4560fd8 to
514b736
Compare
514b736 to
4be6370
Compare

Summary
prime lab setupcreate, select, or bind an active Lab project unless--no-projectis passedprime eval push --eval-idavoids implicit reassignmentReview notes
This PR intentionally contains only the default UX layer on top of #730. The explicit projects CLI, API clients, assignment commands, and explicit
--projectplumbing live in #730.Validation
uv run pytest packages/prime/tests/test_rl_config.py packages/prime/tests/test_lab_setup.py packages/prime/tests/test_eval_push.py packages/prime/tests/test_hosted_eval.py packages/prime/tests/test_projects_cli.py packages/prime/tests/test_rl_api.py packages/prime/tests/test_deployments.py packages/prime-evals/tests/test_evals.py -quv run ruff check packages/prime/src/prime_cli/commands/rl.py packages/prime/src/prime_cli/lab_setup.py packages/prime/src/prime_cli/commands/evals.py packages/prime/src/prime_cli/utils/eval_push.py packages/prime/src/prime_cli/verifiers_bridge.py packages/prime/tests/test_lab_setup.py packages/prime/tests/test_eval_push.py packages/prime/tests/test_hosted_eval.pyNote
Medium Risk
Changes default project attachment for new training runs and evaluations; users who relied on no project must use --no-project or project clear, but eval-id push avoids silent reassignment.
Overview
Default Lab project UX so authenticated workspaces get an active project without a separate
prime project createstep, and new train/eval artifacts attach to it unless opted out.prime lab setupnow runs project setup via_ensure_setup_project: when logged in it creates a project named from the workspace folder (or reuses the matching slug), honors--project/--project-name, and skips with--no-project. It respects a workspace that previously ranprime project clear(stored as a cleared flag in context instead of deleting context).Train and eval paths resolve the active workspace project by default (
resolve_project_id(..., use_active_project=True)onprime train,prime eval run, and mostprime eval pushflows).prime eval push --eval-iddoes not implicitly attach the active project, avoiding accidental reassignment on updates. Post-run hub upload defaults to using the active project as well.README and CLI help text document
--no-projectand the setup flags.Reviewed by Cursor Bugbot for commit 4be6370. Bugbot is set up for automated code reviews on this repo. Configure here.